Move tests location #500
Closed
Move tests location #500
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Considering we are putting the tests inside pelican now maybe we should make their imports fully qualified instead of relative? |
|
yes, we should do that. Assigning myself. |
ghost
assigned 
wking
added a commit
to wking/pelican
that referenced
this pull request
Mar 6, 2013
This brings the docs back up to date after 547f8d2 (Move the tests into pelican. Fix getpelican#500, 2013-04-06).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As we discussed on irc last time, I suggest that we move the tests inside pelican.tests, to avoid some weird things when testing (like not using the right version of pelican for instance).
Also, gentoo packagers will be happier :)